See if turning off: View🞃    Options…        ☐ Graphics [Set] speeds things up. If so, network graphic imports are the suspect. ... View more

gimpfam: However, when the development team tries to add it to the product to the build, the following error displays: What application is reporting this? I get the impression that it's something unrelated to FM, that is trying to integrate the generated HTML5 into some web framework. I've never seen the following error from FM, which more commonly just renders a “?” when it can't render the intended glyph. re: A string was provided with characters that are not available in the specified database code page '1252'. That's referring to Microsoft Windows Code Page 1252, described to a useful level in the Wiki Windows-1252 page. That character set is the pre-Unicode 8-bit set that has ASCII in the low half, and Latin extensions in the upper. That error tends to suggest that whatever this processing code is, it's expecting only single-byte characters. While FM still only supports Unicode BMP, that includes 1, 2, 3 & 4-byte characters. Indeed many characters commonly used in FM, formerly in CP1252 (e.g. ƒ†‡™˜•) are now in Unicode, and would be output as UTF-8, 2-bytes each at least. ... View more

ashrae-editor: I unticked "Allow room for sideheads" in the object properties for both master pages and switched back to body page view, specifiying to remove overrides.  Did you perform a Format🞃 Page Layout› Apply Master Pages… This can also be done from the Update Book menu. ... View more

Thanks for the clarification. So, of these: U+00D0 Ð LATIN CAPITAL LETTER ETH U+00F0 ð LATIN SMALL LETTER ETH U+0110 Đ LATIN CAPITAL LETTER D WITH STROKE U+0111 đ LATIN SMALL LETTER D WITH STROKE the problem is U+0110. I'm not an XML user, but did create an FM2022 .fm document with those text strings. It Published to PDF with no issue (and a correct Đ), but curiously, when Saved As PDF, it never completed, repeatedly … using Source Serif Pro font. It worked OK using Noto Serif. ... View more

It's likely of no use to you at all, esp. in Structured, but FM does ‘know’ how to implement arbitrary numbering, because it's supported in Format🞃Document>Numbering…/Footnote Numbering\ [Custom] Pattern: ABCDEFGHJKLMNOPQRSTUVWXYZ These can then be cross-referenced by $paranum or $paranumonly. But it's all a bit of a hack, usually requiring book meta-content not published, and resulting in hypertext that goes nowhere. It can be handy for fixed-range numbering using arbitrary Unicode character sequences, such as: ❶❷❸❹❺❻❼❽❾❿⓫⓬⓭⓮⓯⓰⓱⓲⓳⓴ Fixed? Yeah, the rollover after ⓴ here would be to ❶❶, and not to ❷❶. There's no way to get it to usefully pick up the ⓿ either. ... View more

Is any Character Format applied? It might also be worthwhile to copy the two out of the resulting PDF or HTML page, and use one of the code converter sites to report its actual codepoint. What would be expected is: U+00D0 Ð LATIN CAPITAL LETTER ETH U+00F0 ð LATIN SMALL LETTER ETH But if this is, for example, a legacy FM document originally using \x notation and a latin extensions codepage/overlay font, various scenarios might apply. ... View more

default38…: Graphics format is ".jpg" (Created with Photoshop / Illustrator and SolidWorks Composer) Checking into the format details of a few might be worthwhile. JPEG has a surplus of options, not all supported by FM. While this is almost certainly not your situation, I reported a case, on the now-gone FM forum here, of what appeared to be a photo-res grayscale image that looked fine in FM, but collapsed to a very blocky 10dpi at the print shop. It turned out to be a JPEG2000, RGB color space, Indexed color, with all R,B&G values identical. FM doesn't support indexed jpg. Re-save from Photoshop fixed it. ... View more

PNG won't work. It's an RGB only format. If your workflow is to color hardcopy, you may need to stay with formats that encode as CMYK. Just opening and re-saving older TIFFs in Photoshop might clear up the problem. I haven't looked into what the optimal modern graphic file format is for CMYK, but it might be PDF (which also has the advantage of being easily previewed on pretty much any platform, which TIFF is not). EPS would also work, but is being phased out. PSD would work too, but is far less portable. ... View more

Winfried: Is there any difference between TIFF files which are scaled correctly and those which have a different dpi/scaling? Indeed, and I might add: if these are newly created images, why is TIFF being used (vs. PNG)? There can be valid reasons to use TIFF, such as needing CMYK or other non-RGB color model. Other reasons represent obscure options in the format, that may not be well supported by the FM import filter. As the Wiki page for TIFF notes, the name could be seen to stand for Thousands of Incompatible File Formats. ... View more

Team…uchc: What is the "assigned paster page", if I can ask? Perhaps what was meant is Apply Master Pages (AMP), an operation that you can run separately: Format🞃 Page Layout › Apply Master Pages… or as an option in the Edit🞃 Update Book › ☑Apply Master Pages I never do it from Update Book.   Performing an AMP might generate some informative complaints. ... View more

FM is likely using whatever is the default browser on your machine (which might not be Edge). Is there anything unusual about it? ... View more

It might be about the adobe.customershome.com/community or adobe-community.customershome.com site, which may be inaccessible at the moment due to a recent erroneous 3rd party domain blacklisting … and is a different domain from community.adobe.com which hosts this forum. ... View more

This could be hacked by not using autonumbering as expected. You'd need a set of list mimic formats, relying on /Basic\ Next Paragraph Tag: [______] to advance the count by invoking a para with the next number.   For a situation where, say 3 is maximum for a list, and 6 is a worst case scenario, you would have ¶formats named: Numbered.01, format [‹n=1›.\t], for which Next is: Numbered.02, format [‹n=2›.\t], for which Next is: Numbered.03, format [‹n=3›.\t], for which Next is: Numbered.w04, format [(Warning - High Count) ‹n=4›.\t], for which Next is: Numbered.w05, format [(Warning - High Count) ‹n=5›.\t], for which Next is: Numbered.w06, format [(Warning - High Count) ‹n=6›.\t], for which Next might be something unusual, perhaps just Body.   This works, although I didn't explore how to get the prefix phrase italicized.   The ‹…› above are not ASCII brackets, to prevent the forum engine from interpreting them. So don't copy&paste them. ... View more

Paragraph Designer /Pagination\ Start: [____] Is one of the controls for where a para will be placed. If you ever use the Insert🞃Page Break… feature, it applies /Pagination\ Start: [Top of Page] to the currently selected para, as an override; not obvious, and easily lost. FM has no page break metadata object per se, as some other DTPs and WPs do.   There are multiple things that control where a para appears on a page. When not desired, it usually turns out that FM is doing what some author told it to do, at some point in the document's history. ... View more

Before investing a lot of effort in implementing the Arabic version of the document in FM, assess what Arabic characters it requires. If you only need characters from these Unicode blocks, FM can do that: Arabic (U+0600–06FF, 256 characters) Arabic Supplement (U+0750–077F, 48 characters) Arabic Extended-B (U+0870–089F, 42 characters) Arabic Extended-A (U+08A0–08FF, 96 characters) Arabic Presentation Forms-A (U+FB50–FDFF, 631 characters) Arabic Presentation Forms-B (U+FE70–FEFF, 141 characters)   If you need anything from these, FM cannot presently do it (FRMAKER-10976): Rumi Numeral Symbols (U+10E60–10E7F, 31 characters) Arabic Extended-C (U+10EC0-10EFF, 7 characters) Indic Siyaq Numbers (U+1EC70–1ECBF, 68 characters) Ottoman Siyaq Numbers (U+1ED00–1ED4F, 61 characters) Arabic Mathematical Alphabetic Symbols (U+1EE00–1EEFF, 143 characters) InDesign probably can handle them all. ... View more

The table will be anchored to a paragraph of some format, often empty and only apparent if Text Symbols are enable to show the ⊥. What are the Keep With Next/Prev settings for that anchor para? … and the para following the rogue table? ... View more

Can you work around it by having the list present twice: once as Generated, but not part of book, and once as part of book, but not generated (or even as text Inset) This workflow might require double Updates (which I do anyway, for other reasons). There is of course the wide question of how these page-oriented assets are presented in a content-oriented context like HTML. Hyperlinks only? ... View more

Matt: An extremely rare correction to one of Bob's posts… Thanks for the correction.  I have to be mistaken from time to time so that I'm not mistaken for an AI… …oh, wait. ... View more

stephen: My file was saved as "filename.fm.492." It is 0 bytes in size. If it's 0 bytes, it's empty, and there's nothing to open. It may be too late, but when you open an existing document, FM automatically creates a .backup. file of it. So even if the in-process file gets totally trashed, you can at least get back to what the session started with… …if you preserve/rename the .backup. file before doing anything else. Else, if you just try to open a trashed .fm, FM will instantly and gleefully trash the prior .backup. If you are on a journaling file system, you may have other recourse.   On auto-save, in a networked-FS situation, auto-save can't save any faster than a manual save. For documents that contain only referenced graphics, this shouldn't be a huge timesink. Embedded graphics are another matter, and another reason why they are worth avoiding. ... View more

I'd mock one up and look, but had a PC migration forced by failing video, and don't have any FMs running on the new machine yet. FM has to have some way identifying and isolating auto-update regions (compared to, say, a manually created in-line TOC, where only the hypertext would be updated, and the whole thing would not be re-written). I'm guessing that there is some MiniTOC-specific ‹tags› that could be searched for in MIF. ... View more

What key tags set off a MiniTOC in MIF? ... View more

As an experiment, you might try re-saving some of the EPS files as SVG, and see if it behaves any differently. If it works, they could be batched in Illustrator, and it would also make the document ready to flow to XML or HTML with the charts remaining vectors, and not getting trashed to raster.   On the other hand, text in SVGs can be a pain to work with, as the embedding is not as slam-dunk as EPS. But Adobe is sunsetting support for EPS, so the move will need to be made eventually. For much of what I do, I end up having Illustrator default to convert-to-outlines when saving to SVG. ... View more

Being a Unicode font just means that some code points above \xFF (U+00FF) are populated. Unicode presently defines 154998 codepoints. No font populates all of Unicode, and today, couldn't even if it wanted to, because OpenType has a limit of 65536 per font. FM has a further problem of not being able to render anything above BMP U+FFFF (FRMAKER-10976), but in this case U+25B6 is in the covered BMP space. The average Unicode font only populates a small fraction of the codespace, and when using anything not on your keyboard, you need to verify that the document font(s) populate each codepoint of interest. Custom enterprise fonts are notoriously stingy. This requires checking MS CharacterMap, BabelMap, or FM CharacterPalette. When the enterprise style guide specifies a font that doesn't populate some codepoint needed, then the author needs to find a style-matching font that does, and continue to apply a Character Format as needed. My practice is to use an FM variable for all needed non-keyboard characters. This approach works around both the stingy font and BMP problems. For autonumber bullets, the Variable approach is inapplicable. Use \u notation plus the dialog's Character Format. Why doesn't this seem to be a problem on the web? Because web browsers do ‘font fallback’, quietly substituing missing a glyph from some other font available on the user's system. FM, and most other authoring apps, don't do fallback, will just give you a “?”. ... View more

If you ever need to flow that document to HTML, or perhaps an eBook format, that triangle won't work at all. It will be rendered as “4”, due to using that old overlay/codepage font substitution. Even if someone copies the text out of a PDF today, it will usually paste as “4”. Consider removing the Character Format from the Autonumber Format and instead using a native Unicode right-pointing triangle, perhaps: ▶ U+25B6 Black Right-pointing Triangle ▸ U+25B8 Black Right-pointing Small Triangle For the former example, this would be an AN Format of: [\u25b6\t] which will collapse to [▶\t] as soon as you enter it. Your Body font does need to populate the code point, however. ... View more

Another approach would be to have multiple red colors of different names. You'll of course have the default “Red” in FM, but you could define a “Red.Change” of the same or similar color values. ... View more